home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
lan
/
merc130.zip
/
MERCNDS.INI
< prev
next >
Wrap
INI File
|
1996-06-23
|
8KB
|
175 lines
# Sample NDS Mode MERCURY.INI file (in fact, the one I use on
# my production server). This one implements most of the possible
# switches for each module, but you can edit it to do less if you
# wish. All the fields shown below are described in the file
# MGUIDE.EXE which is supplied in the Mercury archive.
#
# Anything after a '#' to the end of the line is a comment and
# is stripped out before parsing. Trailing and leading whitespace
# is also stripped before parsing.
#
# Note that the NDS version of Mercury expects NDS names to be expressed
# relative to the root of the NDS tree unless explicitly noted. This
# is especially true for the User ID of the Postmaster - you MUST use
# a full username relative to the Root of the NDS tree for the Postmaster.
[General]
myname: clio.pmail.gen.nz # Canonical name for this server
timezone: +1100 # Time Zone to add to date fields
file_api: 1 # Use the file api instead of queues
mailqueue: SYS:SMTPMAIL # Where mail should be put for delivery
smtpqueue: SYS:SMTPMAIL # Where the SMTP client should look for mail
# debug: 1
# mailqueue: TEMPQ
# smtpqueue: TEMPQ
# note: smtpqueue and mailqueue can be the same
[Mercury]
failfile: SYS:SYSTEM/MERCURY/FAILURE.MER # Delivery failure notification template
confirmfile: SYS:SYSTEM/MERCURY/CONFIRM.MER # Delivery confirmation template
aliasfile: SYS:SYSTEM/MERCURY/ALIAS.MER # System-wide alias file
synfile: SYS:SYSTEM/MERCURY/SYNONYM.MER # User synonym database
listfile: SYS:SYSTEM/MERCURY/LISTS.MER # List of lists
logfile: SYS:SYSTEM/MERCURY/MERCURY.LOG # Traffic logging file
bitnethost: cunyvm.cuny.edu # Relay host for ".bitnet" rewrites
poll: 10 # Seconds between queue polling cycles
scratch: SYS:SYSTEM/MERCURY # Where we can write temp files
switch: 2 # number of ms to yield per op on heavy I/O
returnlines: 15 # How many lines of failed messages to return
postmaster: admin.pmail # NetWare UIC of postmaster relative to Root.
broadcast: 1 # Yes, we want broadcast notifications, but
receipts: 0 # ... no broadcasts for receipt confirmations
PM_notify: 1 # Do/Don't send errors to the postmaster
change_owner: 1 # Change message ownership to recipient
noticeboards: SYS:PUBLIC/NB # Where to find Pegasus Mail noticeboards
automaintenance : 1
# NetWare 4.1 user information
#
# The [NDS] Section of MERCURY.INI is only used in NetWare NDS mode. It
# can be omitted in many cases, since Mercury will prompt for the values
# set in the section if they are absent.
#
# Under NetWare 4.1, Mercury has to login to Directory Services as a
# user object. The account Mercury uses must have sufficient privilege
# to perform the following tasks:
#
# * Scan, Create, Read, Rename and Delete files in every
# user's new mailbox directory
# * Read the "home directory" attribute for every mail user
# to which it might be called upon to deliver mail
# * Search the NDS tree (i.e, have Browse and Read rights) in
# all contexts in which it might operate
# * Read all members of any group to which it may be called
# upon to deliver mail
# * If running in automaintenance mode, it must be able to add
# and delete NDS attributes for any user to which it may
# deliver mail, and create and delete ACLs on any mail user's
# "home directory" NDS attribute.
#
# If you omit the "password" field, Mercury will prompt for it at
# startup time.
#
# Note that you must enter the Mercury User ID as an NDS name expressed
# RELATIVE TO THE ROOT OF YOUR NDS TREE - there is no default context.
#
# Two other options affecting NDS-mode operation are also available in
# other sections of MERCURY.INI:
#
# In the [General] Section:
# "Mailbox_Mode", value 0 or 1, default 0. If 0, Mercury will use the
# new mailbox directory structure created by MAKEMBOX and PMUSER. If
# 1, Mercury will assume that you have loaded the NetWare 4.1 MHS
# Services product and will deliver to the mailbox structure created
# by that system. NOTE: this does NOT mean that Mercury will act as
# an MHS<-->SMTP gateway - it will NOT. It simply controls where it
# will place incoming mail.
#
# In the [Mercury] section:
# "Automaintenance", value 1 or 0: if non-zero, Mercury will automatically
# create new mail directories for users when it detects that they need
# them, using the same logic as the PMUSER NLM. If 0, sending mail to
# a user with no new mail directory currently created will result in
# an error.
[NDS]
UserID : Admin.pmail
[MercuryC]
host: 192.156.225.2 # mail mail host which relays for us
scratch: SYS:SYSTEM/MERCURY # Where we can write temp files
poll: 30 # Seconds between queue polling cycles
switch: 2 # number of ms to yield per op on heavy I/O
returnlines: 15 # How many lines of failed messages to return
failfile: SYS:SYSTEM/MERCURY/FAILURE.MER # Delivery failure template
esmtp: 1 # Yes, we want to use ESMTP extensions
[MercuryS]
switch: 2
debug: 1 # Whether or not to show session progress
# allow: 192.156.225.2 # A machine we WILL permit to connect
# refuse: 192.156.225.0 # A group of machines we WON'T permit.
logfile: SYS:SYSTEM/MERCURY/MERCURYS.LOG
size: 1500000
[MercuryP]
scratch : SYS:SYSTEM/MERCURY
switch : 2
[Groups]
testgroup : Test_group.pmail
# The [Domains] section: Mercury uses the entries in this section to
# work out what addresses it should regard as local (i.e, to which it
# should attempt delivery rather than passing it on). The section is
# simply a table that maps Internet domain names onto the contexts
# in the NDS tree that are associated with that Internet domain.
#
# Defining domains for NetWare 4.1:
# Mercury can service an unlimited number of NDS contexts on your
# network, provided the NDS usercode you provide it with has sufficient
# privilege to be able to access all mail users in those contexts. Each
# context may have its own domain name, and it is possible to have a
# domain name which applies to all organizational units in and below a
# given context.
#
# The [Domains] syntax for NetWare 4.1 is simply an NDS context on the
# left hand side, and the Internet name by which it is known to Internet
# hosts on the right hand side. You may have multiple Internet domain
# names that resolve to the same NDS context, and you can have a single
# Internet domain name that maps to multiple NDS contexts, but only if
# usernames are unique in all the contexts mapped by that domain.
# If you want a domain definition to apply to all organizational units
# (contexts) below the specified context as well as that context, prefix
# the context name with a '/' character - so the entry:
#
# /dev.pmail : dev.pmail.gen.nz
#
# indicates that the Internet domain "dev.pmail.gen.nz" applies to the
# context "dev.pmail", and to any context below it in the NDS tree.
[Domains]
# Context Domain name
/pmail : CLIO
/pmail : clio.pmail.gen.nz
/pmail : [192.156.225.24]
mac.dev.pmail : macstuff.pmail.gen.nz
sales.pmail : sales.pmail.gen.nz
[Maiser]
Maiser : Maiser
Helpfile : SYS:SYSTEM/MERCURY/MAISER.HLP
Lookupfile : SYS:SYSTEM/MERCURY/MAISER.LKP
Send_dir : SYS:SYSTEM/MERCURY/SENDABLE
Logfile : SYS:SYSTEM/MERCURY/MAISER.LOG
Notify : SYS:SYSTEM/MERCURY/TMP
L